home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.hardware
- Path: news-1.csn.net!ub!dsinc!scala!news
- From: dave.haynie@scala.com (Dave Haynie)
- Subject: Re: Iomega ZIP drive and AFS
- Sender: news@scala.scala.com (Usenet administrator)
- Message-ID: <1996Mar21.220737.11756@scala.scala.com>
- Date: Thu, 21 Mar 1996 22:07:37 GMT
- Reply-To: dave.haynie@scala.com (Dave Haynie)
- References: <4ha8n7$8u2@sdaw04.seinf.abb.se> <3149D6B6.44A1@pop.gpnet.it>
- Nntp-Posting-Host: gator
- Organization: Scala Computer Television, US Research Center
-
- In <3149D6B6.44A1@pop.gpnet.it>, Mark Marin <megavolt@pop.gpnet.it> writes:
- >Johan H=96gberg wrote:
-
- >> When formatting a ZIP with AFS file system (AmiFileSafe) 88MB
- >> becomes free. When formatting a ZIP with FFS file system 95MB
- >> becomes free.
-
- >From what I have read, it sets aside room for directory files. THey are
- >all together so you get faster access to the files.
-
- That's correct. The FFS design is to use distributed file management,
- which allocates pieces needed to track a disk's content as needed,
- anywhere on the disk. The AFS design allocates everything can ever use
- up front. However, AFS uses much less overheard to track files and
- their contents.
-
- >> The 95MB value is verified and true. 94 files of each 1024*1024
- >> bytes was copied into 10 directories. After that there was
- >> still 0.5MB free.
-
- Under FFS with 512 byte blocks, your storage requirements go like
- this:
-
- 10 directories 5120 bytes
- 94 file headers 48128 bytes
- 94 1024*1024 data 102760448 bytes
- 94*28 extension blocks 1347584 bytes
-
- Total 104161280 bytes
-
- That is significantly more than the 100 decimal-MB you would expect in
- a drive like this. But, interestingly enough, dead nuts on with a disk
- of 100 binary-MB.
-
- So, you screwed up somewhere. Either the ZIP drive is 100MB, decimal,
- and you're wrong about that little test, or it's 100MB, binary, and
- someone's lying about the storage (100MB decimal rounds off to 95MB
- binary, which is what everyone's claiming the OS tells you).
-
- >It's a feature, not a problem! This is because AmigaDOS uses disk space
- >in 512 (or higher) chunks. A file that is 12 bytes long still takes up
- >512 bytes. With AFS, it only uses the bytes it needs, since several
- >files can all share that 512 byte `block'.
-
- That's also wrong. AFS does store more than one file/directory entry
- per block. But the actual contents of a file are stored in even
- blocks, just as under FFS. Since AFS uses extents, though, which are
- in the reserved area, there's nothing like an extension block
- overhead. And ideally, it takes AFS about 3 longwords, aside from the
- file header data (in the directory list), to store a file of any
- length. It gets worse with fragmentation, but it's not going to be as
- bad as FFS, overhead-wise, in any realistic situation, on a per file
- basis.
-
- Of course, you can probably find a few cases in which FFS stores more
- data than AFS, simply because AFS has a fixed overhead, while FFS's
- grows based on the number and type of its contents.
-
- Dave Haynie | ex-Commodore Engineering | for DiskSalv 3 &
- Sr. Systems Engineer | Hardwired Media Company | "The Deathbed Vigil"
- Scala Inc., US R&D | Ki No Kawa Aikido | info@iam.com
-
- "Feeling ... Pretty ... Psyched" -R.E.M.
-
-